Repository navigation
fix: update uv for PyPI attestation compatibility - #26
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problème
La publication de
0.1.7a échoué pendant la génération des attestations PEP 740 :https://github.com/tducret/allocine-python/actions/runs/41606474349
Le workflow installe uv
0.12.19, incompatible avec certaines options dupyproject.tomldeastral-sh/attest-actionv0.0.7 (require-build-hashes, configuration du cutoff). Cela provoque une tentative de résolution puis un échec avec--locked. Le verrouillage concerné est celui de l’action, pas celui du package. L’étape d’envoi vers PyPI n’a pas été exécutée.Correction
origin/mainaprès la fusion de feat: expose initial theatrical release date on movies #25.0.12.19vers0.13.7dans les quatre installations : contrôles qualité, matrice de tests, construction et publication.Validation locale
Avec uv
0.13.7:uv sync --locked --no-dev --dry-run --project <attest-action>réussit sur le commit exact de l’action utilisé par le workflow (39b6ce43875c196a579e31635b11aa2a2036384a).pytest: 48 tests réussis, 16 snapshots validés.0.13.7.git diff --check: OK.La signature OIDC et l’envoi PyPI ne sont pas exécutés localement ; ils seront validés sur GitHub Actions lors de la prochaine publication.
Après fusion
Créer un nouveau tag
0.1.8surmainpour déclencher le workflow corrigé. Ne pas déplacer0.1.7: une simple relance de son workflow utiliserait toujours l’ancienne configuration.